I understand that MLs are old-skool technology and their use has greatly declined so, even though the overhead of posting release announcments to the MLs is very small, ... progress. We should keep in mind, though, that these MLs are documented at various spots in our documentation and our website, so those refs should be updated, and the mailing lists are cross-posted to other media, like gmane.* and Usenet groups, so the size of the readership for the MLs is difficult to estimate and it may make sense to provide a longer transition period.

@ned-deily Would it be ok to only post to the Announcements mailing list?

Would it be ok to only post to the Announcements mailing list?

@willingc, sure. As long as other Python-related projects are still posting to the Announcements mailing list, we probably should continue to.

Posting to python-announce@ is the thing we're talking about stopping. Part of the reason is the hassle of crafting the message, because the markup is different from discourse/the blog. The blog is awkward for its own reasons, but at least it's editable. Email is not.

The release script could just generate a templated plain text email that essentially just contains a link to the nicely-formatted Discourse and/or blog post. But it wouldn't be the end of the world if it didn't.